You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
In nearby chat (or an IM or a group chat), type in the text
{ test }
Note that there is a space after the opening curly brace and a space before the closing curly brace.
Also test typing this text into a notecard and a script.
Observed Behaviour
The viewer removes the space after "test" as soon as you type in the closing curly brace.
See Fig 1 attached.
Expected Behaviour
I should be able to add a space character before a closing curly brace.
Other Information
This bug doesn't appear to reproduce on all systems but those it reproduces on, it will consistently reproduce.
I can reproduce it on my Windows 7 SP 64bit desktop system (given in system info above) and my Windows 10 64bit laptop.
One of the Firestorm beta testers found this bug & when everyone was testing it in chat, some Windows 7 users and some Windows 10 users could not reproduce it, others could.
On both my systems which reproduce this bug on Second Life 4.0.1 (310054), the bug does not reproduce on pre-CHUI viewers.
I cannot reproduce it on LL viewer Second Life 3.2.8 (248931) Feb 9 2012 09:04:17 (PRE-CHUI) and on Firestorm 4.4.2 (ancient old release).
See Fig 2 attached showing the bug not reproducing on LL viewer Second Life 3.2.8 (248931).
Fwiw, bug does reproduce on Second Life 3.7.7 (289441) Apr 22 2014 11:15:59 (PreInteresting)
This was the earliest build I had still installed that was post-CHUI.
Unable to add a space before closing curly brace in chatbar, notecards & scripts.
Type
Bug
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
Whirly Fizzle (whirly.fizzle)
Created at
2016-03-14T03:49:32Z
Updated at
2016-03-14T16:50:00Z
{
'Business Unit': ['Platform'],
'Date of First Response': '2016-03-13T23:52:13.961-0500',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Viewer',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'Filling in...',
'What were you doing when it happened?': '...',
'What were you expecting to happen instead?': '...',
}
The text was updated successfully, but these errors were encountered:
It's weird. You can make a space before a right brace but you have to make 2 spaces to do one space. Whatever you do, it goes back one space. la la la } la la becomes la la la} la la. la la la } la la becomes la la la } la la
Steps to Reproduce
In nearby chat (or an IM or a group chat), type in the text
{ test }
Note that there is a space after the opening curly brace and a space before the closing curly brace.
Also test typing this text into a notecard and a script.
Observed Behaviour
The viewer removes the space after "test" as soon as you type in the closing curly brace.
See Fig 1 attached.
Expected Behaviour
I should be able to add a space character before a closing curly brace.
Other Information
This bug doesn't appear to reproduce on all systems but those it reproduces on, it will consistently reproduce.
I can reproduce it on my Windows 7 SP 64bit desktop system (given in system info above) and my Windows 10 64bit laptop.
One of the Firestorm beta testers found this bug & when everyone was testing it in chat, some Windows 7 users and some Windows 10 users could not reproduce it, others could.
On both my systems which reproduce this bug on Second Life 4.0.1 (310054), the bug does not reproduce on pre-CHUI viewers.
I cannot reproduce it on LL viewer Second Life 3.2.8 (248931) Feb 9 2012 09:04:17 (PRE-CHUI) and on Firestorm 4.4.2 (ancient old release).
See Fig 2 attached showing the bug not reproducing on LL viewer Second Life 3.2.8 (248931).
Fwiw, bug does reproduce on Second Life 3.7.7 (289441) Apr 22 2014 11:15:59 (PreInteresting)
This was the earliest build I had still installed that was post-CHUI.
Attachments
Original Jira Fields
The text was updated successfully, but these errors were encountered: