246 KiB
246 KiB
| 1 | id | task_title | comment_text | date_created | AuthorPHID | TaskPHID | comment_type | text_for_analysis | cleaned_messages | priority | priority_score | date_closed | CloserPHID | status | time_flag | source | phase | author_closer | same_author | week_index | http_flag | olmo_cleaned_sentences | resolution_outcome | comment_index | isAuthorWMF | cleaned_sentences | human_label | isEdgeCase | ECRationale |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 10828 | 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 | 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! | 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! | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 7 | NA | ['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!"] | NA | 3 | TRUE | The good news: CirrusSearch is updated a few seconds after a page is added, changed, or deleted. | OBSERVED BUG BEHAVIOR | ||
| 3 | 10828 | 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 | 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! | 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! | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 7 | NA | ['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!"] | NA | 3 | TRUE | The bad news: it isn't ready yet! | INVESTIGATION AND EXPLORATION | ||
| 4 | 837 | 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 | Re-checked on https://www.mediawiki.org/wiki/VisualEditor/Team - seems to be fixed. | Re-checked on URL - seems to be fixed. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 71 | NA | ['Re-checked on URL - seems to be fixed.'] | NA | 5 | FALSE | Re-checked on URL - seems to be fixed. | BUG REPRODUCTION | ||
| 5 | 1278 | 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 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=54160 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: URL | Needs Triage | 90 | 1408666032 | NA | declined | True | c1 | 3 | True | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL'] | FALSE | 89 | TRUE | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs. | EXPECTED BEHAVIOR | ||
| 6 | 1278 | 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 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=54160 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: URL | Needs Triage | 90 | 1408666032 | NA | declined | True | c1 | 3 | True | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL'] | FALSE | 89 | TRUE | Both MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. | MOTIVATION | ||
| 7 | 1278 | 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 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=54160 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: URL | Needs Triage | 90 | 1408666032 | NA | declined | True | c1 | 3 | True | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL'] | FALSE | 89 | TRUE | Vagrant currently has this, but Labs does not. | OBSERVED BUG BEHAVIOR | ||
| 8 | 1278 | 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 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=54160 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: URL | Needs Triage | 90 | 1408666032 | NA | declined | True | c1 | 3 | True | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL'] | FALSE | 89 | TRUE | We should find a way to factor it out so the two environments can share it (possibly with a git submodule). | SOLUTION DISCUSSION | ||
| 9 | 1278 | 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 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=54160 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: URL | Needs Triage | 90 | 1408666032 | NA | declined | True | c1 | 3 | True | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL'] | FALSE | 89 | TRUE | This is a proof of concept for doing this more broadly. | MOTIVATION | ||
| 10 | 1278 | 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 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=54160 | Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs./n/nBoth MW-Vagrant and Labs have cases where a simple single-machine MW+Parsoid+VisualEditor setup is desired. Vagrant currently has this, but Labs does not. We should find a way to factor it out so the two environments can share it (possibly with a git submodule). This is a proof of concept for doing this more broadly. -------------------------- **Version**: unspecified **Severity**: enhancement **See Also**: URL | Needs Triage | 90 | 1408666032 | NA | declined | True | c1 | 3 | True | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL'] | FALSE | 89 | TRUE | --------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL | OBSERVED BUG BEHAVIOR | ||
| 11 | 1279 | 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 | 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). | 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). | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 59 | NA | ['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)."] | NA | 140 | TRUE | Yeah. | SOCIAL CONVERSATION | ||
| 12 | 1279 | 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 | 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). | 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). | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 59 | NA | ['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)."] | NA | 140 | TRUE | 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). | INVESTIGATION AND EXPLORATION | ||
| 13 | 960 | 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 | Move VisualEditor Selenium test to VisualEditor repository./n/nRequested by James Forrester at QA mailing list: http://lists.wikimedia.org/pipermail/qa/2013-August/000339.html -------------------------- **Version**: unspecified **Severity**: normal | Move VisualEditor Selenium test to VisualEditor repository./n/nRequested by James Forrester at QA mailing list: URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1377696492 | NA | resolved | True | c1 | 3 | True | False | 8 | NA | ['Move VisualEditor Selenium test to VisualEditor repository.', 'Requested by James Forrester at QA mailing list:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 4 | TRUE | Move VisualEditor Selenium test to VisualEditor repository. | SOLUTION DISCUSSION | ||
| 14 | 960 | 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 | Move VisualEditor Selenium test to VisualEditor repository./n/nRequested by James Forrester at QA mailing list: http://lists.wikimedia.org/pipermail/qa/2013-August/000339.html -------------------------- **Version**: unspecified **Severity**: normal | Move VisualEditor Selenium test to VisualEditor repository./n/nRequested by James Forrester at QA mailing list: URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1377696492 | NA | resolved | True | c1 | 3 | True | False | 8 | NA | ['Move VisualEditor Selenium test to VisualEditor repository.', 'Requested by James Forrester at QA mailing list:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 4 | TRUE | Requested by James Forrester at QA mailing list:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal | SOCIAL CONVERSATION | ||
| 15 | 964 | 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 | Resolved in https://gerrit.wikimedia.org/r/#/c/81486/ | Resolved in URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 8 | NA | ['Resolved in URL'] | NA | 5 | TRUE | Resolved in URL | TASK PROGRESS | ||
| 16 | 8334 | 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL 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 | Medium | 50 | 1380845963 | NA | resolved | True | c1 | 3 | True | False | 0 | 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, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.', 'Note that this only applies to existing content- merging identical annotations in new content is fine.', '--------------------------\n**Version**: unspecified\n**Severity**: normal'] | FALSE | 113 | TRUE | VisualEditor: round-trip adjacent and nested annotations. | OBSERVED BUG BEHAVIOR | ||
| 17 | 8334 | 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL 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 | Medium | 50 | 1380845963 | NA | resolved | True | c1 | 3 | True | False | 0 | 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, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.', 'Note that this only applies to existing content- merging identical annotations in new content is fine.', '--------------------------\n**Version**: unspecified\n**Severity**: normal'] | FALSE | 113 | TRUE | VisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. | EXPECTED BEHAVIOR | ||
| 18 | 8334 | 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL 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 | Medium | 50 | 1380845963 | NA | resolved | True | c1 | 3 | True | False | 0 | 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, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.', 'Note that this only applies to existing content- merging identical annotations in new content is fine.', '--------------------------\n**Version**: unspecified\n**Severity**: normal'] | FALSE | 113 | TRUE | Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff. | OBSERVED BUG BEHAVIOR | ||
| 19 | 8334 | 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL 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 | Medium | 50 | 1380845963 | NA | resolved | True | c1 | 3 | True | False | 0 | 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, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.', 'Note that this only applies to existing content- merging identical annotations in new content is fine.', '--------------------------\n**Version**: unspecified\n**Severity**: normal'] | FALSE | 113 | TRUE | Note that this only applies to existing content- merging identical annotations in new content is fine. | INVESTIGATION AND EXPLORATION | ||
| 20 | 8334 | 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, 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 | VisualEditor: round-trip adjacent and nested annotations./n/nVisualEditor needs to preserve adjacent (even if identical) and additive elements that it internally treats as annotations. Right now it often removes nested annotations (bug 49755) or merges adjacent annotations (bug 49873, URL 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 | Medium | 50 | 1380845963 | NA | resolved | True | c1 | 3 | True | False | 0 | 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, URL\n\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.', 'Note that this only applies to existing content- merging identical annotations in new content is fine.', '--------------------------\n**Version**: unspecified\n**Severity**: normal'] | FALSE | 113 | TRUE | --------------------------\n**Version**: unspecified\n**Severity**: normal | OBSERVED BUG BEHAVIOR | ||
| 21 | 8336 | 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 | 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 | Also, don't cut annotations. This is what I suspect happened here: URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 0 | NA | ["Also, don't cut annotations.", 'This is what I suspect happened here:\nURL'] | NA | 118 | TRUE | This is what I suspect happened here:\nURL | INVESTIGATION AND EXPLORATION | ||
| 22 | 8336 | 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 | 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 | Also, don't cut annotations. This is what I suspect happened here: URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 0 | NA | ["Also, don't cut annotations.", 'This is what I suspect happened here:\nURL'] | NA | 118 | TRUE | Also, don't cut annotations. | ISSUE CONTENT MANAGEMENT | ||
| 23 | 1281 | 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 | [mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.] | [mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.] | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 10 | NA | ['[mass-moving from Tools>MediaWiki-Vagrant to separate product.', 'See bug 54041.', 'Filter bugmail on this comment.]'] | NA | 140 | TRUE | [mass-moving from Tools>MediaWiki-Vagrant to separate product. | SOLUTION DISCUSSION | ||
| 24 | 1281 | 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 | [mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.] | [mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.] | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 10 | NA | ['[mass-moving from Tools>MediaWiki-Vagrant to separate product.', 'See bug 54041.', 'Filter bugmail on this comment.]'] | NA | 140 | TRUE | See bug 54041. | ISSUE CONTENT MANAGEMENT | ||
| 25 | 1281 | 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 | [mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.] | [mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.] | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 10 | NA | ['[mass-moving from Tools>MediaWiki-Vagrant to separate product.', 'See bug 54041.', 'Filter bugmail on this comment.]'] | NA | 140 | TRUE | Filter bugmail on this comment.] | SOLUTION DISCUSSION | ||
| 26 | 3211 | 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 | 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 | Change 75785 had a related patch set uploaded by Catrope: Fix the save button disappearing on certain pages in Firefox GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 3 | NA | ['Change 75785 had a related patch set uploaded by Catrope:\nFix the save button disappearing on certain pages in Firefox\n\nGERRIT_URL'] | NA | 526 | FALSE | Change 75785 had a related patch set uploaded by Catrope:\nFix the save button disappearing on certain pages in Firefox\n\nGERRIT_URL | TASK PROGRESS | ||
| 27 | 3210 | 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 | Change 75785 merged by jenkins-bot: Fix the save button disappearing on certain pages in Firefox https://gerrit.wikimedia.org/r/75785 | Change 75785 merged by jenkins-bot: Fix the save button disappearing on certain pages in Firefox GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 3 | NA | ['Change 75785 merged by jenkins-bot:\nFix the save button disappearing on certain pages in Firefox\n\nGERRIT_URL'] | NA | 527 | FALSE | Change 75785 merged by jenkins-bot:\nFix the save button disappearing on certain pages in Firefox\n\nGERRIT_URL | TASK PROGRESS | ||
| 28 | 965 | 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 | Change 81486 had a related patch set uploaded by Zfilipin: Moved VisualEditor Selenium tests from browsertests repository https://gerrit.wikimedia.org/r/81486 | Change 81486 had a related patch set uploaded by Zfilipin: Moved VisualEditor Selenium tests from browsertests repository GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 8 | NA | ['Change 81486 had a related patch set uploaded by Zfilipin:\nMoved VisualEditor Selenium tests from browsertests repository\n\nGERRIT_URL'] | NA | 716 | FALSE | Change 81486 had a related patch set uploaded by Zfilipin:\nMoved VisualEditor Selenium tests from browsertests repository\n\nGERRIT_URL | TASK PROGRESS | ||
| 29 | 963 | 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 | 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 | Change 81490 had a related patch set uploaded by Zfilipin: Added support for running VisualEditor to Jenkins job template GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 8 | NA | ['Change 81490 had a related patch set uploaded by Zfilipin:\nAdded support for running VisualEditor to Jenkins job template\n\nGERRIT_URL'] | NA | 717 | FALSE | Change 81490 had a related patch set uploaded by Zfilipin:\nAdded support for running VisualEditor to Jenkins job template\n\nGERRIT_URL | TASK PROGRESS | ||
| 30 | 962 | 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 | Change 81490 merged by Cmcmahon: Added support for running VisualEditor tests to Jenkins job template https://gerrit.wikimedia.org/r/81490 | Change 81490 merged by Cmcmahon: Added support for running VisualEditor tests to Jenkins job template GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 8 | NA | ['Change 81490 merged by Cmcmahon:\nAdded support for running VisualEditor tests to Jenkins job template\n\nGERRIT_URL'] | NA | 718 | FALSE | Change 81490 merged by Cmcmahon:\nAdded support for running VisualEditor tests to Jenkins job template\n\nGERRIT_URL | TASK PROGRESS | ||
| 31 | 961 | 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 | Change 81486 merged by jenkins-bot: Moved VisualEditor Selenium tests from browsertests repository https://gerrit.wikimedia.org/r/81486 | Change 81486 merged by jenkins-bot: Moved VisualEditor Selenium tests from browsertests repository GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 8 | NA | ['Change 81486 merged by jenkins-bot:\nMoved VisualEditor Selenium tests from browsertests repository\n\nGERRIT_URL'] | NA | 719 | FALSE | Change 81486 merged by jenkins-bot:\nMoved VisualEditor Selenium tests from browsertests repository\n\nGERRIT_URL | TASK PROGRESS | ||
| 32 | 6268 | 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 | 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 | Change 99596 had a related patch set uploaded by Krinkle: Set up node-jscs, pass it, and configure in local Gruntfile GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 22 | NA | ['Change 99596 had a related patch set uploaded by Krinkle:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL'] | NA | 994 | FALSE | Change 99596 had a related patch set uploaded by Krinkle:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL | TASK PROGRESS | ||
| 33 | 6267 | 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 | Change 99596 merged by jenkins-bot: Set up node-jscs, pass it, and configure in local Gruntfile https://gerrit.wikimedia.org/r/99596 | Change 99596 merged by jenkins-bot: Set up node-jscs, pass it, and configure in local Gruntfile GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 22 | NA | ['Change 99596 merged by jenkins-bot:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL'] | NA | 996 | FALSE | Change 99596 merged by jenkins-bot:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL | TASK PROGRESS | ||
| 34 | 6265 | 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 | 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 | Change 100732 had a related patch set uploaded by Krinkle: Set up node-jscs, pass it, and configure in local Gruntfile GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 23 | NA | ['Change 100732 had a related patch set uploaded by Krinkle:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL'] | NA | 1000 | FALSE | Change 100732 had a related patch set uploaded by Krinkle:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL | TASK PROGRESS | ||
| 35 | 6264 | 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 | Change 100732 merged by jenkins-bot: Set up node-jscs, pass it, and configure in local Gruntfile https://gerrit.wikimedia.org/r/100732 | Change 100732 merged by jenkins-bot: Set up node-jscs, pass it, and configure in local Gruntfile GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 24 | NA | ['Change 100732 merged by jenkins-bot:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL'] | NA | 1017 | FALSE | Change 100732 merged by jenkins-bot:\nSet up node-jscs, pass it, and configure in local Gruntfile\n\nGERRIT_URL | TASK PROGRESS | ||
| 36 | 6263 | 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 | 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 | Change 111963 had a related patch set uploaded by Krinkle: [WIP] Set up node-jscs via Grunt (and pass it) GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 31 | NA | ['Change 111963 had a related patch set uploaded by Krinkle:\n[WIP] Set up node-jscs via Grunt (and pass it)\n\nGERRIT_URL'] | NA | 1093 | FALSE | Change 111963 had a related patch set uploaded by Krinkle:\n[WIP] Set up node-jscs via Grunt (and pass it)\n\nGERRIT_URL | TASK PROGRESS | ||
| 37 | 6262 | 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 | Change 111963 merged by jenkins-bot: Set up node-jscs via Grunt (and pass it) https://gerrit.wikimedia.org/r/111963 | Change 111963 merged by jenkins-bot: Set up node-jscs via Grunt (and pass it) GERRIT_URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 38 | NA | ['Change 111963 merged by jenkins-bot:\nSet up node-jscs via Grunt (and pass it)\n\nGERRIT_URL'] | NA | 1168 | FALSE | Change 111963 merged by jenkins-bot:\nSet up node-jscs via Grunt (and pass it)\n\nGERRIT_URL | TASK PROGRESS | ||
| 38 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | "Leave Feedback" link rendering as two lines in some fonts. | OBSERVED BUG BEHAVIOR | ||
| 39 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | Using Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between \ | BUG REPRODUCTION | ||
| 40 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | User guide\ | NA | ||
| 41 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | and \ | NA | ||
| 42 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | Leave\ | NA | ||
| 43 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | and another one between \ | OBSERVED BUG BEHAVIOR | ||
| 44 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | Leave\ | NA | ||
| 45 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | and \ | NA | ||
| 46 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | feedback\ | NA | ||
| 47 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | . | NA | ||
| 48 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | My very first thought was that \ | SOCIAL CONVERSATION | ||
| 49 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | Leave\ | NA | ||
| 50 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | would be the switch for signing out of the beta test (note that I didn\ | SOLUTION DISCUSSION | ||
| 51 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | s default font: DejaVu Sans. | OBSERVED BUG BEHAVIOR | ||
| 52 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | Arial, so it causes a linebreak in the link. | INVESTIGATION AND EXPLORATION | ||
| 53 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | Maybe one could make that space non-breaking and have the flyout widen instead?" | SOLUTION DISCUSSION | ||
| 54 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal | OBSERVED BUG BEHAVIOR | ||
| 55 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | \n\nThe culprit, evidently is | INVESTIGATION AND EXPLORATION | ||
| 56 | 1354 | "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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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 | "Leave Feedback" link rendering as two lines in some fonts./n/nUsing Firefox 22.0 on Ubuntu 12.04, English Wikipedia User:Hhhippo notes that "I see an empty line between ''User guide'' and ''Leave'' and another one between ''Leave'' and ''feedback''. My very first thought was that ''Leave'' would be the switch for signing out of the beta test (note that I didn't click it ;-)" 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?" URL -------------------------- **Version**: unspecified **Severity**: normal | Needs Triage | 90 | 1374162111 | NA | resolved | True | c1 | 3 | False | False | 2 | 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 ;-)"\n\nThe culprit, evidently is "Ubuntu\'s default font: DejaVu Sans.', "That's a bit wider than e.g.", 'Arial, so it causes a linebreak in the link.', 'Maybe one could make that space non-breaking and have the flyout widen instead?"', 'URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal'] | TRUE | 79 | TRUE | That's a bit wider than e.g. | SOLUTION DISCUSSION | ||
| 57 | 1280 | 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 | 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. | Does ::role::labs::vagrant satisfy this request? Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the CODE command can be used to manipulate roles and run puppet. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 59 | NA | ['Does ::role::labs::vagrant satisfy this request?', 'Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the CODE command can be used to manipulate roles and run puppet.'] | NA | 16 | TRUE | Does ::role::labs::vagrant satisfy this request? | SOLUTION DISCUSSION | ||
| 58 | 1280 | 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 | 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. | Does ::role::labs::vagrant satisfy this request? Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the CODE command can be used to manipulate roles and run puppet. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 59 | NA | ['Does ::role::labs::vagrant satisfy this request?', 'Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the CODE command can be used to manipulate roles and run puppet.'] | NA | 16 | TRUE | Applying it via the wikitech interface provisions the labs host with a copy of MediaWiki-Vagrant and then the CODE command can be used to manipulate roles and run puppet. | SOLUTION DISCUSSION | ||
| 59 | 6258 | 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 | Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :) | Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :) | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 80 | NA | ['Is there work being done to get this run on ci?', "I'd like to push this for Wikibase as well :)"] | NA | 1 | FALSE | Is there work being done to get this run on ci? | TASK PROGRESS | ||
| 60 | 6258 | 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 | Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :) | Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :) | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 80 | NA | ['Is there work being done to get this run on ci?', "I'd like to push this for Wikibase as well :)"] | NA | 1 | FALSE | I'd like to push this for Wikibase as well :) | POTENTIAL NEW ISSUES AND REQUESTS | ||
| 61 | 6256 | 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 | 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/ | Cool, thanks. I added CODE, although I didn't go through grunt since we are not running any other grunt jobs, yet: * Wikibase: URL * integration/config: URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 80 | NA | ['Cool, thanks.', "I added CODE, although I didn't go through grunt since we are not running any other grunt jobs, yet:\n\n* Wikibase: URL\n* integration/config: URL"] | NA | 2 | FALSE | Cool, thanks. | SOCIAL CONVERSATION | ||
| 62 | 6256 | 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 | 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/ | Cool, thanks. I added CODE, although I didn't go through grunt since we are not running any other grunt jobs, yet: * Wikibase: URL * integration/config: URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 80 | NA | ['Cool, thanks.', "I added CODE, although I didn't go through grunt since we are not running any other grunt jobs, yet:\n\n* Wikibase: URL\n* integration/config: URL"] | NA | 2 | FALSE | I added CODE, although I didn't go through grunt since we are not running any other grunt jobs, yet:\n\n* Wikibase: URL\n* integration/config: URL | CONTRIBUTION AND COMMITMENT | ||
| 63 | 10827 | 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 | *** Bug 54777 has been marked as a duplicate of this bug. *** | *** Bug 54777 has been marked as a duplicate of this bug. *** | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 16 | NA | ['*** Bug 54777 has been marked as a duplicate of this bug.', '***'] | NA | 37 | FALSE | *** Bug 54777 has been marked as a duplicate of this bug. | TASK PROGRESS | ||
| 64 | 10827 | 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 | *** Bug 54777 has been marked as a duplicate of this bug. *** | *** Bug 54777 has been marked as a duplicate of this bug. *** | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 16 | NA | ['*** Bug 54777 has been marked as a duplicate of this bug.', '***'] | NA | 37 | FALSE | *** | NA | ||
| 65 | 10826 | 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 | Marking WONTFIX as this is inherently fixed by CirrusSearch and lsearchd has been end of life'd and won't be improved further. | Marking WONTFIX as this is inherently fixed by CirrusSearch and lsearchd has been end of life'd and won't be improved further. | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 17 | NA | ["Marking WONTFIX as this is inherently fixed by CirrusSearch and lsearchd has been end of life'd and won't be improved further."] | NA | 38 | FALSE | Marking WONTFIX as this is inherently fixed by CirrusSearch and lsearchd has been end of life'd and won't be improved further. | ACTION ON ISSUE | ||
| 66 | 6271 | 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 | Is that a replacement for JSHint or unrelated? | Is that a replacement for JSHint or unrelated? | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 11 | NA | ['Is that a replacement for JSHint or unrelated?'] | NA | 95 | TRUE | Is that a replacement for JSHint or unrelated? | INVESTIGATION AND EXPLORATION | ||
| 67 | 6259 | 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 | Sounds good to me Timo. That nicely scale up CI to developers :-) | Sounds good to me Timo. That nicely scale up CI to developers :-) | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['Sounds good to me Timo.', 'That nicely scale up CI to developers :-)'] | NA | 150 | TRUE | Sounds good to me Timo. | SOCIAL CONVERSATION | ||
| 68 | 6259 | 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 | Sounds good to me Timo. That nicely scale up CI to developers :-) | Sounds good to me Timo. That nicely scale up CI to developers :-) | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['Sounds good to me Timo.', 'That nicely scale up CI to developers :-)'] | NA | 150 | TRUE | That nicely scale up CI to developers :-) | SOLUTION USAGE | ||
| 69 | 6257 | 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 | >>! 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 :-) | QUOTE QUOTE 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: URL More details at URL :-) | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 80 | NA | ["QUOTE\nQUOTE\n\nYou 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:\n\nURL\n\nMore details at URL :-)'] | NA | 152 | TRUE | Example:\n\nURL\n\nMore details at URL :-) | OBSERVED BUG BEHAVIOR | ||
| 70 | 6257 | 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 | >>! 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 :-) | QUOTE QUOTE 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: URL More details at URL :-) | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 80 | NA | ["QUOTE\nQUOTE\n\nYou 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:\n\nURL\n\nMore details at URL :-)'] | NA | 152 | TRUE | QUOTE\nQUOTE\n\nYou will need a package.json and a npm 'test' entry point with a devDependencies for grunt-jscs. | BUG REPRODUCTION | ||
| 71 | 6257 | 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 | >>! 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 :-) | QUOTE QUOTE 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: URL More details at URL :-) | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 80 | NA | ["QUOTE\nQUOTE\n\nYou 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:\n\nURL\n\nMore details at URL :-)'] | NA | 152 | TRUE | From there we can add a Jenkins job that invokes 'npm test' and that should run jscs. | SOLUTION DISCUSSION | ||
| 72 | 836 | 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 URL 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 | Needs Triage | 90 | 1415881118 | NA | resolved | True | c1 | 3 | True | False | 11 | 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 URL 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**Version**: unspecified\n**Severity**: normal'] | FALSE | 284 | TRUE | VisualEditor: Dimensions of small images are lost in rendering. | OBSERVED BUG BEHAVIOR | ||
| 73 | 836 | 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 URL 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 | Needs Triage | 90 | 1415881118 | NA | resolved | True | c1 | 3 | True | False | 11 | 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 URL 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**Version**: unspecified\n**Severity**: normal'] | FALSE | 284 | TRUE | Images that have thumbnail sizes that are larger than the original should be rendered at the specified size, not the size of the original. | EXPECTED BEHAVIOR | ||
| 74 | 836 | 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 URL 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 | Needs Triage | 90 | 1415881118 | NA | resolved | True | c1 | 3 | True | False | 11 | 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 URL 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**Version**: unspecified\n**Severity**: normal'] | FALSE | 284 | TRUE | MediaWiki core does this, but somewhere between MediaWiki/Parsoid/VisualEditor the specified dimensions are lost. | OBSERVED BUG BEHAVIOR | ||
| 75 | 836 | 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 URL 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 | Needs Triage | 90 | 1415881118 | NA | resolved | True | c1 | 3 | True | False | 11 | 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 URL 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**Version**: unspecified\n**Severity**: normal'] | FALSE | 284 | TRUE | For example, on URL there are various uses of [[File:Wikimedia_Foundation_office_camera_shy.png]] (of which the full size is 140px). | BUG REPRODUCTION | ||
| 76 | 836 | 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 URL 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 | Needs Triage | 90 | 1415881118 | NA | resolved | True | c1 | 3 | True | False | 11 | 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 URL 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**Version**: unspecified\n**Severity**: normal'] | FALSE | 284 | TRUE | 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. | OBSERVED BUG BEHAVIOR | ||
| 77 | 836 | 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 | VisualEditor: Dimensions of small images are lost in rendering./n/nImages 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 URL 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 | Needs Triage | 90 | 1415881118 | NA | resolved | True | c1 | 3 | True | False | 11 | 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 URL 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**Version**: unspecified\n**Severity**: normal'] | FALSE | 284 | TRUE | --------------------------\n**Version**: unspecified\n**Severity**: normal | OBSERVED BUG BEHAVIOR | ||
| 78 | 6254 | 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee URL 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 | Medium | 50 | 1409154874 | NA | resolved | True | c1 | 3 | True | False | 11 | NA | ['Jenkins: Use node-jscs as checkstyle for javascript coding style.', "See URL\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.", '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.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement'] | FALSE | 286 | TRUE | Jenkins: Use node-jscs as checkstyle for javascript coding style. | EXPECTED BEHAVIOR | ||
| 79 | 6254 | 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee URL 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 | Medium | 50 | 1409154874 | NA | resolved | True | c1 | 3 | True | False | 11 | NA | ['Jenkins: Use node-jscs as checkstyle for javascript coding style.', "See URL\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.", '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.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement'] | FALSE | 286 | TRUE | 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. | CONTRIBUTION AND COMMITMENT | ||
| 80 | 6254 | 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee URL 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 | Medium | 50 | 1409154874 | NA | resolved | True | c1 | 3 | True | False | 11 | NA | ['Jenkins: Use node-jscs as checkstyle for javascript coding style.', "See URL\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.", '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.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement'] | FALSE | 286 | TRUE | --------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement | OBSERVED BUG BEHAVIOR | ||
| 81 | 6254 | 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee 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 | Jenkins: Use node-jscs as checkstyle for javascript coding style./n/nSee URL 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 | Medium | 50 | 1409154874 | NA | resolved | True | c1 | 3 | True | False | 11 | NA | ['Jenkins: Use node-jscs as checkstyle for javascript coding style.', "See URL\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.", '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.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: enhancement'] | FALSE | 286 | TRUE | See URL\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. | SOLUTION DISCUSSION | ||
| 82 | 6270 | Jenkins: Use node-jscs as checkstyle for javascript coding style | Unrelated. | 1379460821 | PHID-USER-sai77mtxmpqnm6pycyvz | PHID-TASK-2mkgo6douokimv6febmw | task_subcomment | Unrelated. | Unrelated. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 11 | NA | ['Unrelated.'] | NA | 287 | TRUE | Unrelated. | SOCIAL CONVERSATION | ||
| 83 | 6269 | 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 | 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]]. | 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]]. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 11 | NA | ['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]].'] | NA | 288 | TRUE | node-jscs would be purely for coding style, not code quality (which is what jshint is primarily for). | SOLUTION DISCUSSION | ||
| 84 | 6269 | 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 | 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]]. | 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]]. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 11 | NA | ['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]].'] | NA | 288 | TRUE | 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). | SOLUTION DISCUSSION | ||
| 85 | 6269 | 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 | 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]]. | 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]]. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 11 | NA | ['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]].'] | NA | 288 | TRUE | 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]]. | EXPECTED BEHAVIOR | ||
| 86 | 6260 | 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 | 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. | 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. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['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.'] | NA | 354 | TRUE | The bug is to figure out how to properly do it. | SOCIAL CONVERSATION | ||
| 87 | 6260 | 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 | 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. | 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. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['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.'] | NA | 354 | TRUE | 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. | SOLUTION DISCUSSION | ||
| 88 | 6260 | 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 | 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. | 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. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['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.'] | NA | 354 | TRUE | Any further repos that want it, can enable it the same way other pipelines are introduced. | SOLUTION USAGE | ||
| 89 | 6260 | 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 | 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. | 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. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['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.'] | NA | 354 | TRUE | By patching their Gruntfile or adding a new npm-test pipeline. | INVESTIGATION AND EXPLORATION | ||
| 90 | 6260 | 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 | 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. | 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. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 60 | NA | ['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.'] | NA | 354 | TRUE | I think we've reached that point. | SOCIAL CONVERSATION | ||
| 91 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | This avoids added complexity, needless abstraction, and indirect dependencies on the underlying framework (e.g. | SOLUTION DISCUSSION | ||
| 92 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | URL\nURL | NA | ||
| 93 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright. | SOCIAL CONVERSATION | ||
| 94 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. | SOLUTION USAGE | ||
| 95 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | which might not work cross-platform if put inside CODE (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. | SOLUTION DISCUSSION | ||
| 96 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | I've recently started to use this more often as well. | SOCIAL CONVERSATION | ||
| 97 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | Only use Grunt when there's a need for it. | SOLUTION DISCUSSION | ||
| 98 | 6255 | 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 | >>! 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 | QUOTE QUOTE QUOTE QUOTE QUOTE That's quite alright. If you don't need do run bash commands like CODE, CODE, CODE, CODE etc. which might not work cross-platform if put inside CODE (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. URL URL | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 88 | NA | ["QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat's quite alright.", "If you don't need do run bash commands like CODE, CODE, CODE, CODE etc.", "which might not work cross-platform if put inside CODE (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.", 'URL\nURL'] | NA | 372 | TRUE | jscs/jshint) which can be quite annoying since it doesn't like being pinned to a direct version that way. | SOLUTION DISCUSSION | ||
| 99 | 10942 | 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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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): URL . Fram (talk) 07:31, 2 August 2013 (UTC) >> -------------------------- **Version**: unspecified **Severity**: enhancement | Low | 25 | NA | NA | open | True | c1 | 3 | False | False | 4 | 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): URL .', 'Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 55 | TRUE | VisualEditor: Disallow (discourage?) | EXPECTED BEHAVIOR | ||
| 100 | 10942 | 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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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): URL . Fram (talk) 07:31, 2 August 2013 (UTC) >> -------------------------- **Version**: unspecified **Severity**: enhancement | Low | 25 | NA | NA | open | True | c1 | 3 | False | False | 4 | 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): URL .', 'Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 55 | TRUE | placing references inside section headers. | OBSERVED BUG BEHAVIOR | ||
| 101 | 10942 | 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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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): URL . Fram (talk) 07:31, 2 August 2013 (UTC) >> -------------------------- **Version**: unspecified **Severity**: enhancement | Low | 25 | NA | NA | open | True | c1 | 3 | False | False | 4 | 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): URL .', 'Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 55 | TRUE | <<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. | EXPECTED BEHAVIOR | ||
| 102 | 10942 | 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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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): URL . Fram (talk) 07:31, 2 August 2013 (UTC) >> -------------------------- **Version**: unspecified **Severity**: enhancement | Low | 25 | NA | NA | open | True | c1 | 3 | False | False | 4 | 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): URL .', 'Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 55 | TRUE | 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). | MOTIVATION | ||
| 103 | 10942 | 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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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): URL . Fram (talk) 07:31, 2 August 2013 (UTC) >> -------------------------- **Version**: unspecified **Severity**: enhancement | Low | 25 | NA | NA | open | True | c1 | 3 | False | False | 4 | 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): URL .', 'Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 55 | TRUE | Example (spam, but the principle applies): URL . | BUG REPRODUCTION | ||
| 104 | 10942 | 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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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 | VisualEditor: Disallow (discourage?) placing references inside section headers./n/n<<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): URL . Fram (talk) 07:31, 2 August 2013 (UTC) >> -------------------------- **Version**: unspecified **Severity**: enhancement | Low | 25 | NA | NA | open | True | c1 | 3 | False | False | 4 | 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): URL .', 'Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 55 | TRUE | Fram (talk) 07:31, 2 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement | OBSERVED BUG BEHAVIOR | ||
| 105 | 10824 | 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< URL 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**: URL | Low | 25 | 1383013054 | NA | declined | True | c1 | 3 | False | False | 6 | NA | ["Newly-uploaded image doesn't immediately appear in image search results in VisualEditor.", '<< URL 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**:\nURL'] | FALSE | 78 | TRUE | << URL is a headshot of Virginia Henderson that was uploaded to Commons yesterday. | SOCIAL CONVERSATION | ||
| 106 | 10824 | 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< URL 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**: URL | Low | 25 | 1383013054 | NA | declined | True | c1 | 3 | False | False | 6 | NA | ["Newly-uploaded image doesn't immediately appear in image search results in VisualEditor.", '<< URL 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**:\nURL'] | FALSE | 78 | TRUE | WhatamIdoing (talk) 00:17, 13 August 2013 (UTC) >>\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL | OBSERVED BUG BEHAVIOR | ||
| 107 | 10824 | 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< URL 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**: URL | Low | 25 | 1383013054 | NA | declined | True | c1 | 3 | False | False | 6 | NA | ["Newly-uploaded image doesn't immediately appear in image search results in VisualEditor.", '<< URL 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**:\nURL'] | FALSE | 78 | TRUE | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor. | OBSERVED BUG BEHAVIOR | ||
| 108 | 10824 | 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< 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 | Newly-uploaded image doesn't immediately appear in image search results in VisualEditor./n/n<< URL 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**: URL | Low | 25 | 1383013054 | NA | declined | True | c1 | 3 | False | False | 6 | NA | ["Newly-uploaded image doesn't immediately appear in image search results in VisualEditor.", '<< URL 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**:\nURL'] | FALSE | 78 | TRUE | VisualEditor's image feature can't find it, and won't accept file names that it doesn't believe exist. | OBSERVED BUG BEHAVIOR | ||
| 109 | 871 | 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 | Request for edit summary preview./n/nA 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 | Request for edit summary preview./n/nA De.WP user suggested to include a preview for the edit summary. Report: URL -------------------------- **Version**: unspecified **Severity**: enhancement | Needs Triage | 90 | 1380545659 | NA | resolved | True | c1 | 3 | False | False | 9 | NA | ['Request for edit summary preview.', 'A De.WP user suggested to include a preview for the edit summary.', 'Report:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 12 | TRUE | Request for edit summary preview. | EXPECTED BEHAVIOR | ||
| 110 | 871 | 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 | Request for edit summary preview./n/nA 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 | Request for edit summary preview./n/nA De.WP user suggested to include a preview for the edit summary. Report: URL -------------------------- **Version**: unspecified **Severity**: enhancement | Needs Triage | 90 | 1380545659 | NA | resolved | True | c1 | 3 | False | False | 9 | NA | ['Request for edit summary preview.', 'A De.WP user suggested to include a preview for the edit summary.', 'Report:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 12 | TRUE | A De.WP user suggested to include a preview for the edit summary. | MOTIVATION | ||
| 111 | 871 | 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 | Request for edit summary preview./n/nA 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 | Request for edit summary preview./n/nA De.WP user suggested to include a preview for the edit summary. Report: URL -------------------------- **Version**: unspecified **Severity**: enhancement | Needs Triage | 90 | 1380545659 | NA | resolved | True | c1 | 3 | False | False | 9 | NA | ['Request for edit summary preview.', 'A De.WP user suggested to include a preview for the edit summary.', 'Report:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement'] | FALSE | 12 | TRUE | Report:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement | OBSERVED BUG BEHAVIOR | ||
| 112 | 3208 | 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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **Version**: unspecified **Severity**: normal **URL**: URL | High | 80 | 1374700983 | NA | resolved | True | c1 | 3 | False | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL'] | TRUE | 58 | TRUE | VisualEditor: Action buttons of the toolbar (including "Save") don\ | OBSERVED BUG BEHAVIOR | ||
| 113 | 3208 | 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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **Version**: unspecified **Severity**: normal **URL**: URL | High | 80 | 1374700983 | NA | resolved | True | c1 | 3 | False | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL'] | TRUE | 58 | TRUE | , "The particular article in the URL field of this bug report doesn | OBSERVED BUG BEHAVIOR | ||
| 114 | 3208 | 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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **Version**: unspecified **Severity**: normal **URL**: URL | High | 80 | 1374700983 | NA | resolved | True | c1 | 3 | False | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL'] | TRUE | 58 | TRUE | The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. | BUG REPRODUCTION | ||
| 115 | 3208 | 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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **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 | VisualEditor: Action buttons of the toolbar (including "Save") don't appear on some articles in Firefox because error is thrown./n/nThe particular article in the URL field of this bug report doesn't not display the Save button in Firefox. The Save button is displayed in Chrome, and it is displayed in other articles in Firefox. -------------------------- **Version**: unspecified **Severity**: normal **URL**: URL | High | 80 | 1374700983 | NA | resolved | True | c1 | 3 | False | False | 3 | 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.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL'] | TRUE | 58 | TRUE | --------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL | OBSERVED BUG BEHAVIOR | ||
| 116 | 3212 | 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 | 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 | Another article where this happens: URL | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 3 | NA | ['Another article where this happens:\n\nURL'] | NA | 59 | TRUE | Another article where this happens:\n\nURL | BUG REPRODUCTION | ||
| 117 | 1355 | "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 | This was already reported as bug 51335 (sorry!). *** This bug has been marked as a duplicate of bug 51335 *** | This was already reported as bug 51335 (sorry!). *** This bug has been marked as a duplicate of bug 51335 *** | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 2 | NA | ['This was already reported as bug 51335 (sorry!).', '*** This bug has been marked as a duplicate of bug 51335 ***'] | NA | 1316 | TRUE | This was already reported as bug 51335 (sorry!). | ISSUE CONTENT MANAGEMENT | ||
| 118 | 1355 | "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 | This was already reported as bug 51335 (sorry!). *** This bug has been marked as a duplicate of bug 51335 *** | This was already reported as bug 51335 (sorry!). *** This bug has been marked as a duplicate of bug 51335 *** | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 2 | NA | ['This was already reported as bug 51335 (sorry!).', '*** This bug has been marked as a duplicate of bug 51335 ***'] | NA | 1316 | TRUE | *** This bug has been marked as a duplicate of bug 51335 *** | ACTION ON ISSUE | ||
| 119 | 3209 | 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 | This is now fixed in master; we will make sure it is deployed tomorrow. | This is now fixed in master; we will make sure it is deployed tomorrow. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 3 | NA | ['This is now fixed in master; we will make sure it is deployed tomorrow.'] | NA | 1399 | TRUE | This is now fixed in master; we will make sure it is deployed tomorrow. | TASK PROGRESS | ||
| 120 | 10829 | 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 | The image now comes up in the search result - this is probably a delay in the speed with which the search index is updated. | The image now comes up in the search result - this is probably a delay in the speed with which the search index is updated. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 7 | NA | ['The image now comes up in the search result - this is probably a delay in the speed with which the search index is updated.'] | NA | 1568 | TRUE | The image now comes up in the search result - this is probably a delay in the speed with which the search index is updated. | INVESTIGATION AND EXPLORATION | ||
| 121 | 8335 | 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 | This has been fixed for some time in the DM. Marking as such. | This has been fixed for some time in the DM. Marking as such. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 13 | NA | ['This has been fixed for some time in the DM.', 'Marking as such.'] | NA | 1793 | TRUE | This has been fixed for some time in the DM. | TASK PROGRESS | ||
| 122 | 8335 | 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 | This has been fixed for some time in the DM. Marking as such. | This has been fixed for some time in the DM. Marking as such. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 13 | NA | ['This has been fixed for some time in the DM.', 'Marking as such.'] | NA | 1793 | TRUE | Marking as such. | ACTION ON ISSUE | ||
| 123 | 10825 | 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 | *** Bug 52218 has been marked as a duplicate of this bug. *** | *** Bug 52218 has been marked as a duplicate of this bug. *** | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 17 | NA | ['*** Bug 52218 has been marked as a duplicate of this bug.', '***'] | NA | 1861 | TRUE | *** Bug 52218 has been marked as a duplicate of this bug. | ISSUE CONTENT MANAGEMENT | ||
| 124 | 10825 | 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 | *** Bug 52218 has been marked as a duplicate of this bug. *** | *** Bug 52218 has been marked as a duplicate of this bug. *** | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 17 | NA | ['*** Bug 52218 has been marked as a duplicate of this bug.', '***'] | NA | 1861 | TRUE | *** | NA | ||
| 125 | 6266 | 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 | 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. | 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. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 22 | NA | ['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.'] | NA | 1973 | TRUE | 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. | TASK PROGRESS | ||
| 126 | 6261 | 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 | 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? | 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? | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 38 | NA | ['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?'] | NA | 2127 | TRUE | 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? | ISSUE CONTENT MANAGEMENT | ||
| 127 | 838 | VisualEditor: Dimensions of small images are lost in rendering | Fixed in 2013. | 1415881118 | PHID-USER-ydswvwhh5pm4lshahjje | PHID-TASK-bd72y7iiei67kbxti76b | task_subcomment | Fixed in 2013. | Fixed in 2013. | NA | NA | NA | NA | NA | True | c1 | 3 | True | NA | 71 | NA | ['Fixed in 2013.'] | NA | 2334 | TRUE | Fixed in 2013. | TASK PROGRESS | ||
| 128 | 872 | 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 | *** This bug has been marked as a duplicate of bug 42139 *** | *** This bug has been marked as a duplicate of bug 42139 *** | NA | NA | NA | NA | NA | True | c1 | 3 | False | NA | 13 | NA | ['\n\n*** This bug has been marked as a duplicate of bug 42139 ***'] | NA | 407 | FALSE | \n\n*** This bug has been marked as a duplicate of bug 42139 *** | ACTION ON ISSUE |