MW 1.43 + CS Master -- Not sure if this is a VE-for-All bug or not, but it manifest in CS when there are multiple CSs in a single page.. if you open more than one CS for comment at the same time, the first CS will save the text from the second CS regardless of what was typed into the CS box.
Description
Details
Related Objects
- Mentioned In
- rECOSec03299720e2: VEForAll puts text in wrong box when multiple are open
rECOS4358b3706429: VEForAll puts text in wrong box when multiple are open
rECOS83c4fbf0d07a: VEForAll puts text in wrong box when multiple are open
rECOSd550603210ba: VEForAll puts text in wrong box when multiple are open
Event Timeline
Change #1233298 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/CommentStreams@master] VEForAll puts text in wrong box when multiple are open
Change #1233298 merged by jenkins-bot:
[mediawiki/extensions/CommentStreams@master] VEForAll puts text in wrong box when multiple are open
Change #1233333 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/CommentStreams@REL1_43] VEForAll puts text in wrong box when multiple are open
Change #1233334 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/CommentStreams@REL1_44] VEForAll puts text in wrong box when multiple are open
Change #1233335 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/CommentStreams@REL1_45] VEForAll puts text in wrong box when multiple are open
Change #1233333 merged by jenkins-bot:
[mediawiki/extensions/CommentStreams@REL1_43] VEForAll puts text in wrong box when multiple are open
Change #1233334 merged by jenkins-bot:
[mediawiki/extensions/CommentStreams@REL1_44] VEForAll puts text in wrong box when multiple are open
Change #1233335 merged by jenkins-bot:
[mediawiki/extensions/CommentStreams@REL1_45] VEForAll puts text in wrong box when multiple are open
I just tested git fetch https://gerrit.wikimedia.org/r/mediawiki/extensions/CommentStreams refs/changes/93/1233393/9 && git checkout -b change-1233393 FETCH_HEAD
and confirmed that this issue has been resolved and can be closed. (Is there something more I can or should do on this issue?)