STORM-1731 Ad-hoc confererence block failing. Residents using it to start massive multi-sim conferences, used as a griefing tool.
Review Request #524 - Created Dec. 12, 2011 and submitted
Jonathan Yap | Reviewers | ||
3.2.5 | viewer | ||
STORM-1731 | |||
None | viewer-development |
Ad-hoc IMs and voice call sessions are established even though you have muted the initiator. The result is that others in the ad-hoc session start writing back to what is usually some provocative message from the initiator and you end up seeing these messages. It has been reported that many IM tabs are also created sometimes.
See test plan in jira. Testing Not Done: regression testing to see if these code changes have broken muting for other circumstances.
Review request changed
Updated (Dec. 12, 2011, 6 a.m.)
Posted (Dec. 12, 2011, 6:42 a.m.)
-
indra/newview/llimview.cpp (Diff revision 1) -
Warning level should be used for potential code or protocol problems. This would be better at Info level.
-
indra/newview/llimview.cpp (Diff revision 1) -
Doesn't it make more sense to put the isMuted check in an outer test, and then the more specific additional checks for voice in the inner check? Also, why is isLinden a special case for voice but not for other sessions?
-
indra/newview/llimview.cpp (Diff revision 1) -
Info level
Review request changed
Updated (Dec. 12, 2011, 11:54 a.m.)
-
- added Diff r2
Updated diff with revised if-muted logic per RB requst.
Review request changed
Updated (Jan. 9, 2012, 1:21 p.m.)
- changed from pending to submitted
Other reviews