Our apologies for any inconvenience. We had hoped to avoid any service interruptions which had occurred as we enhanced our platform to prepare for a rollout of various new upcoming system features including offline messaging. We’re endeavoring to complete these enhancements in smaller increments to further minimize any further interruption
Hello
@punker barbie \n (new line) has stopped behaving as expected on the Test Bed. This behavior shifted about 2-3 weeks ago, or right around the time users started to really complain about connectivity. I am curious if one of the resent changes to the main CB site has resulted in something being overlooked on the Test Bed?
Previous behavior... \n\nHello resulted in
Notice:
Notice: Hello
Current Test Bed behavior... \n\nHello results in
Notice: Hello
I have remained a strong proponent for Test Bed and Public Server unity over the past 2 years. I believe that if something functions on the Public Servers, then it should also function on the Test Bed. In the past, I have received warnings for being away from my cam, while alone in my room, with a password set to test code on the Public server (creepy!) To avoid future warnings, I spend all of my time writing/testing on the Test Bed servers. Sometimes I discover functionality differences that I strive to keep the CB staff aware of. My past efforts have resulted in the ability to create Grey Accounts, to test Anonymous tipping, and off-line (active stream not required) support of both
cb.getRoomOwnerData(func) &
cb.getRoomUsersData(func). Users who write code expect the results they get on the Test Bed to be 100% mirrored by the Public Server. \n has been supported for the entire time I have written code for CB and now behaves differently on the Public Server than on the Test Bed.
I have reported this to CB staff about 1 week ago, and have yet to receive a response. Now that I am aware of the current state of updates, the lack of response makes more sense. However, I do not want this to get over looked. Consistancy is key to providing a user experience free of frustration, be it as a broadcaster or a JavaScript coder.
Cheers,
Cexmental